這 多供應商困境 代表了高階運算（HPC）領域中戰略與技術上的分裂。十餘年來，軟體生態一直呈現單一化；然而，隨著競爭性的艾克薩級硬體如 Frontier 以及 El Capitan （AMD）的出現，加上傳統的 NVIDIA 部署，迫使開發流程產生「分叉」。
1. 硬體異質性與封閉生態
開發者面臨「供應商封閉生態」的問題，導致程式碼在不同架構之間存在物理與邏輯上的不相容。選擇專有介面會導致 供應商鎖定，必須將維護工作加倍，才能支援異質化的叢集環境。
2. 生態系統分裂
系統由彼此排他的環境變數所定義，這會在建置系統中造成衝突：
CUDA_PATH：NVIDIA 工具包的根目錄。HSA_PATH：AMD ROCm 的異質系統架構路徑。
3. 維護債務
移植舊有程式碼庫通常需要完全重寫核心函式與記憶體管理。若缺乏可移植的層級，次級程式碼庫將面臨 位元腐壞 的問題，因創新停滯，工程師又苦於條件編譯的處理。
main.py
TERMINALbash — 80x24
> Ready. Click "Run" to execute.
>
QUESTION 1
What core issue defines the 'Multi-Vendor Dilemma' in HPC?
The lack of high-speed interconnects between nodes.
Software fragmentation caused by incompatible, vendor-specific APIs.
The inability of CPUs to handle floating-point operations.
High power consumption in exascale data centers.
✅ Correct!
Correct. The dilemma arises because code written for one vendor's hardware (e.g., NVIDIA) cannot run on another's (e.g., AMD) without significant modification.❌ Incorrect
The dilemma is specifically about software portability across different hardware vendors like NVIDIA, AMD, and Intel.QUESTION 2
Which environment variable is typically used to locate the AMD ROCm/HSA toolkit?
CUDA_HOMEHSA_PATHAMD_ROOTROCM_LLVM✅ Correct!
HSA_PATH refers to the Heterogeneous System Architecture path essential for the AMD ROCm stack.❌ Incorrect
AMD's ecosystem typically uses HSA_PATH or ROCM_PATH to define its toolkit root.QUESTION 3
What is 'Bit Rot' in the context of HPC maintenance debt?
Physical degradation of GPU memory modules.
The gradual decay of secondary codebases that are not updated for new architectures.
A specific compiler error when using Clang.
Data loss occurring during MPI communication.
✅ Correct!
When developers focus on one architecture, other versions of the code become obsolete and buggy over time.❌ Incorrect
In this context, bit rot is a software maintenance issue where secondary codebases fall behind the primary development branch.QUESTION 4
Why does a 'Vendor Silo' affect HPC build systems?
It requires the use of multiple, mutually exclusive environment variables and toolchains.
It limits the number of nodes a cluster can support.
It forces the use of Python instead of C++.
It eliminates the need for unit testing.
✅ Correct!
Build systems become complex because they must conditionally link against different library paths based on the target hardware.❌ Incorrect
Silos create 'Logical Incompatibility' where build scripts must be rewritten for each specific hardware environment.QUESTION 5
The shift toward AMD hardware in clusters like Frontier and El Capitan has broken which decade-long trend?
The use of Fortran in scientific computing.
The software monoculture dominated by NVIDIA's proprietary environment.
The move toward cloud computing.
The use of Liquid Cooling in supercomputers.
✅ Correct!
The dominance of NVIDIA/CUDA was the standard for years; new competitive hardware has forced a shift toward portability.❌ Incorrect
While Fortran remains, the proprietary software stack 'monoculture' is what has been disrupted by multi-vendor exascale systems.Case Study: The Two-Cluster Dilemma
Infrastructure management at an HPC research center
A researcher writes an atmospheric model for Cluster A (NVIDIA H100). The center then acquires Cluster B (AMD MI300A). The researcher must now support both systems without doubling the engineering time.
Q
1. If the researcher uses standard CUDA, what is the primary obstacle when running on Cluster B?
Solution:
The primary obstacle is source code incompatibility; Cluster B uses the AMD ROCm stack and searches for headers in the HSA_PATH, whereas CUDA is proprietary to NVIDIA hardware.
The primary obstacle is source code incompatibility; Cluster B uses the AMD ROCm stack and searches for headers in the HSA_PATH, whereas CUDA is proprietary to NVIDIA hardware.
Q
2. How does the presence of both CUDA_PATH and HSA_PATH complicate the build system?
Solution:
The build system (e.g., Make or CMake) must be configured with conditional logic to detect the environment and link against the correct vendor-specific libraries, significantly increasing maintenance complexity.
The build system (e.g., Make or CMake) must be configured with conditional logic to detect the environment and link against the correct vendor-specific libraries, significantly increasing maintenance complexity.
Q
3. What is the strategic risk of maintaining two separate source trees for this model?
Solution:
The risk is 'Maintenance Debt' and 'Bit Rot'. Over time, features added to the NVIDIA version may not be ported to the AMD version, leading to inconsistent results and eventual failure of the secondary codebase.
The risk is 'Maintenance Debt' and 'Bit Rot'. Over time, features added to the NVIDIA version may not be ported to the AMD version, leading to inconsistent results and eventual failure of the secondary codebase.